Configuring MSMQ and MSDTC for Distributed Transaction |
|
Before you begin this task:
Load Cordys MSMQTransport.isv
- Install and configure MSMQ.
- To configure MSDTC, do the following:
- Start Services Distributed Transaction Coordinator, Message Queuing, and Message Queuing Triggers from Start > Administrative Tools > Services.
- Go to Start > Administrative Tools > Component Services.
- Expand Component Services. Right-click My Computer and select Properties. The My Computer Properties dialog box appears.
- Click the MSDTC tab, enable Use local coordinator and click OK.
- Go to Distributed Transaction Coordinator.
- Right-click Local DTC and select Properties.
- On the Security Configuration tab, select the Network DTC Access, and Enable XA Transactions check boxes.
- Click OK. The MSDTC service is restarted.
- Restart Message Queueing and Message Queueing Triggers.
- Click OK in the Properties box and close Component Services.
To configure MSDTC for Process Platform, do the following:
- Create a Service Group, Service Container, and Connection Point using the System Resource Manager task.
- While creating a Service Container, place the following jar file in Service Containers JVM classpath:
$CORDYS_HOME\<instancename>\components\msmqtransport\msmqtransport.jar
- Modify the Connection Point Configuration.
- Select MSMQ as the Type. The corresponding input fields change.
- Select the Distributed Transaction option.
- Select the Machine Name.
- Provide the Queue Name. For example, queue1. You must use the same name that you provided while creating the queue using MSMQ.
- Select Private.
- In
wcp.properties
, add two entries for the TransactionManager configuration as follows:com.cordys.xatransaction.TransactionManagerFactory=com.cordys.xatransaction.msdtc.MSDTCFactory com.cordys.xatransaction.msdtc.hostname=<MSDTC hostname>
- Click
and restart the processor.
Note: Ensure that you start and configure the MSDTC service in all the systems that are used in the transaction.
Note: It is possible to configure the Web Gateway so that it can deliver requests into a queue. However, note that the HTTP protocol itself is not reliable; hence this setup does not make the Web Gateway reliable.
If you want to configure the Web Gateway for reliable messaging, do the following:
- In the No Reply and Transaction mode, place
msmqtransport.jar
inbcp.classpath
or system classpath for the Gateway. - While configuring queues, select the user as Everyone and set the permissions as Full Control.